# Using Amazon EMR as a target

The following topics describe how to use Amazon EMR as a target endpoint in a Qlik Replicate task:

Information note

Hive can be configured to use the AWS Glue Data Catalog as its metastore or its own metastore. The metastore that will be used depends on your Amazon EMR Cluster configuration and requires no special configuration from a Replicate perspective.

In this section:

* [Prerequisites](https://help.qlik.com/en-US/replicate/May2025/Content/Replicate/Main/Amazon%20EMR/AmazonEMR_prereq_hadoop_gen_target.htm)
* [Limitations](https://help.qlik.com/en-US/replicate/May2025/Content/Replicate/Main/Amazon%20EMR/AmazonEMR_limitations_hadoop.htm)
* [Change data partitioning on Amazon EMR](https://help.qlik.com/en-US/replicate/May2025/Content/Replicate/Main/Amazon%20EMR/AmazonEMR_Hadoop_CDC_partitioning.htm)
* [Amazon EMR endpoint target data types](https://help.qlik.com/en-US/replicate/May2025/Content/Replicate/Main/Amazon%20EMR/AmazonEMR_hadoop_data_types_target.htm)
* [Setting general connection properties](https://help.qlik.com/en-US/replicate/May2025/Content/Replicate/Main/Amazon%20EMR/AmazonEMR_set_up_hadoop_as_target.htm)
* [Setting advanced connection properties](https://help.qlik.com/en-US/replicate/May2025/Content/Replicate/Main/Amazon%20EMR/AmazonEMR_advanced_prop_hadoop_target.htm)